Skip to content

checkmicroarchitecture: allow AlmaLinux 10 x86-64-v2 targets#156

Merged
andrewlukoshko merged 1 commit into
AlmaLinux:almalinux-ng-0.24.0from
yuravk:almalinux-ng-0.24.0
Apr 20, 2026
Merged

checkmicroarchitecture: allow AlmaLinux 10 x86-64-v2 targets#156
andrewlukoshko merged 1 commit into
AlmaLinux:almalinux-ng-0.24.0from
yuravk:almalinux-ng-0.24.0

Conversation

@yuravk
Copy link
Copy Markdown
Collaborator

@yuravk yuravk commented Apr 20, 2026

AlmaLinux 10 is additionally built for the x86-64-v2 microarchitecture level, so when the upgrade target distro is AlmaLinux the requirement for target major version 10 stays at x86-64-v2 instead of RHEL 10's x86-64-v3. Other target distros (RHEL, CentOS Stream) keep the original x86-64-v3 requirement on 10.

AlmaLinux 10 is additionally built for the x86-64-v2 microarchitecture
level, so when the upgrade target distro is AlmaLinux the requirement
for target major version 10 stays at x86-64-v2 instead of RHEL 10's
x86-64-v3. Other target distros (RHEL, CentOS Stream) keep the original
x86-64-v3 requirement on 10.
@github-actions
Copy link
Copy Markdown

Thank you for contributing to the Leapp project!

Please note that every PR needs to comply with the leapp-repository contribution and development guidelines and must pass all tests in order to be mergeable.
If you want to request a review or rebuild a package in copr, you can use following commands as a comment:

  • review please @oamg/developers to notify leapp developers of the review request
  • /packit copr-build to submit a public copr build using packit

Packit will automatically schedule regression tests for this PR's build and latest upstream leapp build.
However, here are additional useful commands for packit:

  • /packit test to re-run manually the default tests
  • /packit retest-failed to re-run failed tests manually
  • /packit test oamg/leapp#42 to run tests with leapp builds for the leapp PR#42 (default is latest upstream - main - build)

Note that first time contributors cannot run tests automatically - they need to be started by a reviewer.

It is possible to schedule specific on-demand tests as well. Currently 2 test sets are supported, beaker-minimal and kernel-rt, both can be used to be run on all upgrade paths or just a couple of specific ones.
To launch on-demand tests with packit:

  • /packit test --labels kernel-rt to schedule kernel-rt tests set for all upgrade paths
  • /packit test --labels beaker-minimal-8.10to9.4,kernel-rt-8.10to9.4 to schedule kernel-rt and beaker-minimal test sets for 8.10->9.4 upgrade path

See other labels for particular jobs defined in the .packit.yaml file.

Please open ticket in case you experience technical problem with the CI. (RH internal only)

Note: In case there are problems with tests not being triggered automatically on new PR/commit or pending for a long time, please contact leapp-infra.

@yuravk yuravk requested a review from andrewlukoshko April 20, 2026 07:44
@andrewlukoshko andrewlukoshko merged commit 98e8208 into AlmaLinux:almalinux-ng-0.24.0 Apr 20, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants